Skip to content

External Secrets Operator config #967

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 15 commits into from
Apr 30, 2025
Merged

External Secrets Operator config #967

merged 15 commits into from
Apr 30, 2025

Conversation

pricem14pc
Copy link
Contributor

@pricem14pc pricem14pc commented Nov 15, 2024

What and why?

Changing ExternalSecret to use the cluster secret store pattern to facilitate migration to the External Secrets Operator and to align with other ExternalSecrets.

See this PR for testing

@pricem14pc pricem14pc requested a review from a team as a code owner January 9, 2025 12:58
@anwilkie anwilkie changed the title Moved ExternalSecret config to cluster-setup External Secrets Operator config Mar 21, 2025
@anwilkie anwilkie self-requested a review April 1, 2025 14:28
Copy link
Contributor

@arroyoAle arroyoAle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Secrets get collected from the new replicator in performance and the current one in dev

@pricem14pc pricem14pc merged commit 395d045 into main Apr 30, 2025
3 checks passed
@pricem14pc pricem14pc deleted the external-secrets-io branch April 30, 2025 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants